Repository navigation
config: one local.conf for every operator choice, not endless flags - #8
Merged
Merged
Conversation
A deployment's settings were scattered across machine.env (generated), engagement.env, ambient registry variables, and a growing list of build-tiered.sh flags. Collapse them into a single file, client/local.conf: every SPEAR_* choice in one place, documented, the ones not made left commented. - local.conf.example (was machine.env.example) is the full menu: deployment paths, the image-tier choices, and the push registries, grouped and commented. - Every consumer -- spear-chat, spear-corpus, build.sh, build-tiered.sh and spear-image -- sources local.conf, falling back to machine.env so a host configured the old way keeps working. - build-tiered.sh reads each former flag from the environment (SPEAR_COMMONS, SPEAR_ENTITY, SPEAR_BAKE, SPEAR_PROJECT_TREES, ...); a flag still overrides it, so `spear-image build base` alone works once local.conf names the commons and entity. - spear-configure writes local.conf, migrating an existing machine.env's hand-made settings and seeding the commented menu from the example on a first run. - The tracked template names no organisation or build system; the real, untracked local.conf on a host carries those.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A deployment's settings were scattered across
machine.env(generated),engagement.env, ambient registry variables, and a growing list ofbuild-tiered.shflags. This collapses them into one file,client/local.conf: everySPEAR_*choice in one place, documented, the ones not made left commented.Changes
client/local.conf.example(renamed frommachine.env.example) — the full menu: deployment paths, image-tier choices, and push registries, grouped and commented.local.conf, falling back tomachine.envso a host configured the old way keeps working:spear-chat,spear-corpus,build.sh,build-tiered.sh,spear-image.build-tiered.shreads each former flag from the environment (SPEAR_COMMONS,SPEAR_ENTITY,SPEAR_BAKE,SPEAR_PROJECT_TREES,SPEAR_FROM_BASE,SPEAR_STANDARDS_STORE,SPEAR_LICENSED,SPEAR_KNOWLEDGE,SPEAR_TAG); a flag still overrides it. Oncelocal.confnames the commons and entity,spear-image build basealone is enough.spear-configurewriteslocal.conf, migrates an existingmachine.env's hand-made settings, and seeds the commented menu from the example on a first run..gitignoreignoreslocal.conf/.bak.acme/registry.example.com); the real, untrackedlocal.confon a host carries those.Tests
test_launcher_environment: updated for thelocal.conf-then-machine.envsourcing, plus a precedence test (local.confwins) and gitignore coverage forlocal.conf.main— the 5 pre-existing failures (staletest_spear_imageassertion,test_environment_namespaceallowlist, andpublic_boundaryoffenders from earlier merges) are unchanged; this branch adds none, andlocal.conf.exampleis not among the boundary offenders.